Re: svn commit: r773881 - in /httpd/httpd/branches/2.2.x: CHANGES

am 22.05.2009 19:17:07 von Jeff Trawick

--000e0cd2c052230175046a836e5e
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On Thu, May 21, 2009 at 3:25 PM, Jeff Trawick wrote:

>
>
> On Thu, May 21, 2009 at 3:08 PM, William A. Rowe, Jr. > > wrote:
>
>> Jeff Trawick wrote:
>> > Does somebody else care to share their opinion on this? Which of these
>> > are okay?
>> >
>> > - existing mod_perl releases (and potentially other third-party modules)
>> > won't compile with 2.2.12
>>
>> CORE_PRIVATE may be broken from release to release, it's a necessary
>> concession to prevent utter stagnation :(
>
>
> The bits are not CORE_PRIVATE.
>
> You can find sample Perl code on the web that even tests these bits, though
> it isn't clear to me if that is a normal practice when using the
> Perl/mod_include interface.
>

Hmmm, after trying to use what seems like a cool feature, I find that
mod_perl was never taught to use the Apache 2's mod_include plug-in
interface.

--000e0cd2c052230175046a836e5e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, May 21, 2009 at 3:25 PM, Jeff Tr=
awick <trawick@gm=
ail.com> wrote:

"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padd=
ing-left: 1ex;">

On Thu, May 21, 2009 a=
t 3:08 PM, William A. Rowe, Jr. < we@rowe-clan.net" target=3D"_blank">wrowe@rowe-clan.net> wrot=
e:

204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">

Jeff Trawick wrote:

> Does somebody else care to share their opinion on this? =A0Which of th=
ese

> are okay?

>

> - existing mod_perl releases (and potentially other third-party module=
s)

> won't compile with 2.2.12

CORE_PRIVATE may be broken from release to release, it's a necess=
ary

concession to prevent utter stagnation :(

The bi=
ts are not CORE_PRIVATE.

You can find sample Perl code on the web th=
at even tests these bits, though it isn't clear to me if that is a norm=
al practice when using the Perl/mod_include interface.

Hmmm, after trying to use what seems like a coo=
l feature, I find that mod_perl was never taught to use the Apache 2's =
mod_include plug-in interface.

--000e0cd2c052230175046a836e5e--